Specific Options

This section contains the specific options concerning:

• A2L parser plug-in
• API server plug-in
• ASCET plug-in
• ASCET@FUSION plug-in
• Assessment engine plug-in
• AUTOSAR plug-in
• Batch test execution
• Build plug-in
• Check for compile errors
• CCode plug-in
• Data converter plug-in
• INCA plug-in
• MATLAB plug-in
• Report plug-in

A2L parser plug-in

The A2L parser plug-in imports an A2L file into TPT. The options are basically the same as in the import interface. If you just specify a TPT file and an A2L file, all signals are imported. In case you only want to import a selection of signals, specify an interface file. If no mapping is stated, a new mapping will be created. Additionally, a parameter file can be imported. The following default settings apply:

• parameter will always be "exchange"
• array signals will not be split
• missing signals will be created

Available if called with --run a2lparser:

<tpt>

The TPT file to load.

<a2l>

The A2L file to parse.

(-i|--interface) <interface>

The interface file to preselect inputs and outputs.

(-p|--parameter) <parameter>

The parameter file (DCM or HEX) to load parameter values.

(-m|--mapping) <mapping>

Name of the target mapping that will be filled. If no mapping is specified, TPT will create one.

(-l|--platform) <platform>

Name of the platform where system constant values shall be stored.

Example:

tpt.exe --run a2lparser c:\temp\test.tpt c:\temp\test.a2l --platform P1 --interface c:\temp\test.txt

This configuration will import all symbols contained in test.txt interface file from the test.a2l file into the test.tpt project file. System constant values will be assigned to platform P1.

API server plug-in

--apiPort <apiPortFlag>

Specify the port for the TPT API. Default is 1099. The TPT API will be activated.

--apiBindingName <apiBindingNameFlag>

Specify the binding name for the TPT API. The TPT API will be activated.

--run apiserver <apiRunScript> arg1 arg2 arg3

To run an API script enter the path where <apiRunScript> is the path. Arguments can be added to make scripts more flexible.

--remote --run apiserver <apiRunScript>

To open and run the script in a currently running TPT.

--remote <apiRunScript>

To open the script in a currently running TPT instance.

<apiRunScript>

To open the script in the API Script Editor of a new TPT instance.

ASCET plug-in

--useAnyAscetversion

If the ASCETversion selected in the platform config is not defined in this TPT installation and only one ASCET version is installed. This version will be used.

--run ascet <tptfile>

TPT file to process.

--run ascet --genTestframe <AscetPlatformConfiguration>

ASCET Platform configuration name.

Generates the test frame for the ASCET project specified in the ASCET configuration.

ASCET@FUSION plug-in

Available if called with --run ascetfusion:

<tptfile>

TPT file to process.

--genTestframe <Ascet@FusionPlatformConfiguration>

ASCET@FUSION Platform configuration name.

Generates the testframe for the ASCET@FUSION project specified in the Platform Configuration dialog.

Assessment engine plug-in

Available if called with --run assessmentengine:

script1 script2 ... scriptN

Starts the assessment engine and executes the Python scripts script1, script2, and so forth one after the other.

(-v|--var) <vardef> ... script1 script2 ...

Starts the assessment engine and executes the Python scripts script1, script2, and so forth one after the other. If one or more variables have been defined with the option -v or --var, these definitions are also passed to the scripts. For example, the argument --var foo = bar defines the variable foo throughout all scripts and assigns it the value bar.

–-convert tptfile1, tptfile2, ..., tptfileN

Translates all assessment scripts found within the given TPT model file from the old assessment language used in early versions of TPT into the new Python-based assessment language, introduced with version 2.0 of TPT.

AUTOSAR plug-in

Available if called with --run autosar:

<tptfile>

TPT file to process.

--genTestframe <AUTOSARConfiguration >

AUTOSAR Platform configuration name.

[<x32> or <x64>]

The desired architecture. If the architecture is not given, the architecture of the configuration is used. Generates and compiles the test frame for the given AUTOSAR Platform configuration.

Build plug-in

You can use --run build with many options. The syntax is as follows:

tpt.exe --run build <path to the TPT file> <name of the execution configuration> --<option1> --<option2>

Example:

tpt.exe --run build C:\tools\examples\DASHBOARD\batch\demo.tpt Race --doDashboard yes

This will run the file demo.tpt with the execution configuration named Race in the Dashboard view and automatically close the file when the test execution is finished.

Available if called with --run build:

<tptfile>

TPT file that contains the configuration that shall be executed.

<Configuration Name>

Name of the execution configuration.

You cannot enter the path to an execution configuration in an execution configuration folder. Thus,"Group_A/My Execution Configuration One" is not allowed. The execution configuration name must be unique.

-v|--verbose

Output logs to command line.

--v0

No output to command line.

--v1

Dump error logs to command line.

--v2

Output test cases in progress and error logs to command line (default).

--v3

Output full logs to command line (same as -v|--verbose).

-o |--overviewonly

This option generates only an overview report. Always execute the test case before, so that test data and report data of the test cases are available. Whenever you execute TPT with the option --run build, a test case summary is available at the end of execution, showing how many tests are PASSED, FAILED, or INCONCLUSIVE.

Example:

--run build myTPTfile.tpt example-execution-configuration –o

-s|--showProgress

Show the progress dialog.

--doExec <doExec>

Execute test cases [yes|no]?

For example, --doExec yes.

--doDebug <doDebug>

DEPRECATED - has no effect.

Exists only to be able to accept this flag for compatibility.

--doAssess <doAssess>

Assess test cases [yes|no]?

For example, --doAssess no.

--doReport <doReport>

Generate report [yes|no]?

For example, --doReport no.

--doDashboard <doDashboard>

Run test execution with the TPT dashboard [yes|no]?

For example, --doDashboard yes.

--doTestmanagement <doMgmt>

Generate test management information [yes|no]?

For example, --doTestmanagement no.

--doSkipSuccessfulTestcases <doSkipSuccess>

Skip all test cases that have been assessed to be successful already [yes|no]?

For example, --doSkipSuccessfulTestcases no.

--dataDir <dataDir>

Data directory, for example, --dataDir C:\tools\dataDir.

--reportDir <reportDir>

Report directory.

For example, --reportDir C:\tools\reports.

--testSet <testSet>

Specify a test set that should be used by the execution configuration. If the execution configuration has multiple execution items, the test set will be used for every item, for example, --testSet MyTestSetOne.

You cannot enter the path to a test set in a test set folder. Thus, --testSet "Group_A/MyTestSetOne" is not allowed. The test set name must be unique.

--cores <cores>

Specify the number of cores to be used during test execution.

For example, --cores 4.

--reportFormat <reportFormat>

Report format can be pdf, html, pdf_allinone, html_embedded.

--dataDirStructure <dataDirStructure>

Structure of the data directory can be HIERARCHICAL_WITH_INDEX, HIERARCHICAL_WITH_ID, FLAT_WITH_INDEX, FLAT_WITH_ID, FLAT_ONLY_ID or FLAT_WITH_INDEX_AND_ID.

[--headless]

Start TPT with an apiserver without UI.

Batch test execution

Available if called with --run batch:

<tptbatchfile>

The batch file created in the Batch Runner view can be executed, see Views - Batch Runner.

Check for compile errors

--run compiler <TPT file>

TPT file that should be checked for compile errors. The syntax is as follows:

tpt.exe --run compiler <the path to your TPT project file>.

The exit code has the following flags:

first bit	a general error occurred, e.g. unable to open the given file
second bit	at least one test case has compile errors
third bit	at least one assesslet (w/o globally deactivated) has compile errors

The compile errors found will be printed to the standard error stream.

CCode plug-in

Available if called with --run ccode:

<tptfile>

TPT file to process.

--genTestframe <CPlatformConfiguration>

C/C++ Platform configuration name.

Generates the test frame for the given C/C++ Platform configuration.

Data converter plug-in

Available if called with --run dataconverter:

<inputfile>

Input file that contains test data in one of the supported formats.

<outputfile>

Output file for conversion results.

(-f|--format) <format>

Format is a specific identifier depending on the format to be exported, for example, 'to-workspace' for MAT files.

(-s|--split) <split>

If the input file format is TPTBIN, this option can be used to split data chunk longer than the specified duration.

Example:

--split=10 s

Splits the whole file in multiple files each with a time interval of 10 s.

--run dataconverter inputfile outputfile (-f|--format) format-id

Provides a command line interface, allowing the conversion of data files like test records and measurements, from one file format to another. It is possible to select one of several output file types on the basis of the file extension; the input file type is parsed automatically.

Allowed file types are TPTBIN, MAT, CSV. The format-id specifies details about the export format. Especially for MAT-format to-workspace exports to MATLAB to-workspace format.

Example:

tpt.exe --run dataconverter myinfile.tptbin myoutfile.mat --format to-workspace

Furthermore, TPTBIN files may be split into smaller files using the option —split or -s:

tpt.exe --run dataconverter --split=10000s c:\temp\a.tptbin c:\temp\aout.tptbin.

When a testing run takes long, test data size tends to be very big. TPT might be unable to read such big files of several gigabytes. Use the -split option to chop the TPT data in smaller chunks:

--split=10000s

TPT data is chopped every 10000 seconds.

c:\temp\a.tptbin

Indicates the location of the TPT data to be chopped.

c:\temp\aout.tptbin

Indicates the output folder where the chopped data will be placed,
in the form of:

aout_000_(0s-10000s).tptbin

aout_001_(10000s-20000s).tptbin

aout_001_(20000s-30000s).tptbin

INCA plug-in

--incaConfiguration <incaConfiguration>

Specify INCA configuration to be used in FUSION Platform with INCA Client Node.

--incaUseActive

Use currently active INCA workspace in FUSION Platform with INCA Client Node.

MATLAB plug-in

--closeMatlabAfterTestrun

Force to close MATLAB after a test run invoked from the command line

--matlabport <matlabport>

Specify the TCP port to be used for MATLAB communication.

--run matlab <tptfile>

TPT file to process.

--run matlab --importInterface <MatlabPlatformConfiguration>

MATLAB configuration name.

Imports the interface with the settings specified in the MATLAB configuration and saves the TPT file.

--run matlab --genTestframe <MatlabPlatformConfiguration>

MATLAB configuration name.

Generates the test frame for the model specified in the MATLAB configuration.

--run matlab --genFusionDLL <MatlabPlatformConfiguration>

MATLAB configuration name.

Generates the FUSION DLL for the model specified in the MATLAB/Simulink Platform configuration. To generate the FUSION DLL you can also use the Build model for FUSION button in the Platform Configuration dialog, see Build a MATLAB/Simulink model for FUSION.

Report plug-in

Available if called with --run report:

<sourcedir>

Root directory of the source report directories.

(-d|--targetdir) <targetdir>

Directory where the overview should be generated (default is sourcedir).

-m|--multiExec

Generate an overview HTML report over all test executions.

The sourcedir can be a list of folders which will be searched for test data folders recursively. A test data folder is recognized by the test_summary_xml file. If no target directory is given the first folder of sourcedir is assumed to be target directory. The tree structure located on the left-hand side of the report is derived from the file system.

Example:

--run report "C:\temp\examples\foo;C:\foo\Documents" --targetdir "C:\temp\examples" -m